Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Greptile OverviewGreptile SummaryThis PR implements secret version value redaction to combat secret spill by allowing users to redact (clear) secret values from historical versions while keeping metadata intact. The implementation also fixes a bug where automatic secret reference updates weren't incrementing versions correctly. Key changes:
Bug fix details: Confidence Score: 4/5
Important Files Changed
|
Additional Comments (4)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Fix: only set
Fix: replace this with a non-regex split/join (e.g.
The route response is declared as Fix: explicitly map/strip the returned |
|
@greptile, your additional comments:
Answer: Wrong. The route only accepts JWT auth (user auth)
Answer: This is fine. In this case we don't use the response for invalidation
Answer: Doesn't matter, it matches a single char. But I've refactored it to use .replaceAll instead
Answer: Wrong. Even if the encryptedValue is included in the object, zod just strips it out so it's not returned in the request. This is the design we follow across the whole API.
|
Context
Added support for redacting secret value versions. We update the actual secret value in-place of the secret version, and mark it as redacted. This is done to combat secret spill and avoid storing secret values elsewhere than just the latest secret version.
This PR also incldues a fix for the automatic updating of secret references not incrementing secret versions correctly.
Steps to verify the change
Type
Checklist
type(scope): short description(scope is optional, e.g.,fix: prevent crash on syncorfix(api): handle null response).